Hi Kevin,
Both are possibilities. The functionality that is shown on the KMotionCNC Tool Setup Screen allows such things as setting bits and calling a C Program in KFLOP. But there is no screen to help set it up. You must configure the information programmatically. The information is stored in a table of "MCode_Actions". I haven't looked at if/how it is exposed in KMotion_dotNet. There was also a new type of action that can simply make a call back to you to do whatever you want.
Regards
TK
| Group: DynoMotion |
Message: 3016 |
From: fireup_kev |
Date: 1/9/2012 |
| Subject: Re: M Code in KMotion_dotNet |
Tom,
I don't see that these features are exposed in KMotion_dotNet. When I it sees an M6, it should at lease pause and allow the event to happen and then allow a way to continue, but it just zips right through it...
Kevin
--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Kevin,
> Â
> Both are possibilities. The functionality that is shown on the KMotionCNC Tool Setup Screen allows such things as setting bits and calling a C Program in KFLOP. But there is no screen to help set it up. You must configure the information programmatically. The information is stored in a table of "MCode_Actions". I haven't looked at if/how it is exposed in KMotion_dotNet. There was also a new type of action that can simply make a call back to you to do whatever you want.
> Â
> Regards
> TK
>
>
> ________________________________
> From: fireup_kev <kliboon@...>
> To: DynoMotion@yahoogroups.com
> Sent: Monday, January 9, 2012 9:35 AM
> Subject: [DynoMotion] M Code in KMotion_dotNet
>
>
> Â
> How is M Codes handled in KMoiton_dotNet? When it sees a M6 for example, does it send a callback, call a C Program in KFLOP?
>
> Thanks,
> Kevin
> |
|
| |
